Google Workspace Integration FAQ
This is a frequently asked question when implementing and operating SHIELD DRM in a Google Workspace environment. For questions unrelated to cloud services, please refer to the "Basic FAQ on SHIELD DRM."
Integration
Q1. Why are a service account and domain-wide delegation needed for integration?
SHIELD DRM must detect changes in Google Drive and process documents on the server even when the user is not logged in. The standard way to access the organization's Drive in Google Workspace isService Account + Domain-wide Delegationis.
- The service account is operated by SHIELD DRM.The customer does not need to create a Google Cloud project or service account.
- The customer company has a scope for the client ID of the SHIELD DRM service account in the Google Admin Console.
https://www.googleapis.com/auth/driveis approved once. - My drive is this delegation.Owner's Authorityto borrow and handle, the shared drive isService Account Nameis processed.
The procedure is "Google Workspace Pre-Guideof사전 준비 #5Please refer to.
Q2. Should the administrator account be handed over to SHIELD DRM?
No, the administrator isApprove full delegation of the domain only onceIt is necessary. The integrated administrator account used by SHIELD DRM during operation hasDrive 및 문서You only need administrator privileges. Only the email address is provided, not the password.
Q3. There is an unknown account in the shared drive member list.
SHIELD DRM service account. When you install the channel on the shared drive, SHIELD DRM will service the account.참여자automatically added.**Do not delete or lower the role.**If deleted, the document processing for that drive will fail. Service accounts do not consume Google Workspace licenses.
Action
Q4. The document is not being processed in the shared drive.
Please check in the following order.
- Admin Page
연동 관리→Google Drive 이벤트 채널→공유 드라이브The status of the drive in the tab is설치I confirm recognition. - SHIELD DRM service account in shared drive member
참여자Check if there is any. If not or if the role is low, release the channel and reinstall it. - If the shared drive is blocking access for users outside the organization, you cannot add service accounts. Check the shared drive settings.
- Checks if there are conditional policies targeting the specified drive and whether the uploaded document is a DRM document.
Q5. The newly created shared drive is not automatically protected.
New shared drive has**The channel is not installed automatically.**The new shared drive appears in the admin page list every hour, and동기화will appear immediately when executed. After appearing in the list, the administrator채널 설치will be processed from that time. The same goes for the new user's My Drive.
Q6. It takes a long time for the document to be processed.
If you hit the Google Drive API quota due to bulk uploads, SHIELD DRM will automatically retry, which may delay the reflection. For detailed causes and responses, see 「Google Workspace API Quota InformationPlease refer to 」.
Q7. The notification channel expires after 7 days, do I need to reinstall it periodically?
No, SHIELD DRM automatically re-registers the channel before expiration. There is nothing for the administrator to do.
Q8. After the document was processed, the editor changed to my name or a strange account.
This is because SHIELD DRM has reflected the document that has been decrypted as a new version in the same file.
- My drive is processed with owner permissions, so the modifierOwner本人is recorded.
- Shared drives areSHIELD DRM Service Accountis recorded.
The file name, location, and sharing settings remain the same.
Protection Method
Q9. Are the documents uploaded to Google Drive kept in an encrypted state?
No. SHIELD DRM in the Google Workspace environment is the policy-targeted DRM document of theDecryptMake it viewable and editable in Google Drive. It does not provide the ability to encrypt documents or convert them to MIP labels at the time of upload.
Q10. Why is the downloaded document re-encrypted?
At the time of downloading from Google Drive to PCDocument Security (Endpoint) reapplies DRM protectionbecause of this. In the cloud, encryption is disabled for collaboration, and documents that come out on PCs are protected again. The re-protection criteria are in the admin page.조건부 정책 → Endpoint → Document SecurityIt is a policy.
Q11. How are Google Drive labels and MIP labels different?
| item | Google Drive Label | MIP Label (Microsoft 365) |
|---|---|---|
| Personality | Classification Metadata | Classification + Protection |
| Encryption | not done | ham |
| Access Control | not done | ham |
Drive labels are used to classify and search documents and do not protect documents. The Google Workspace policy of SHIELD DRM does not grant or retrieve Drive labels.
Q12. Are files attached in Google Chat also processed?
No, Google Chat attachments are not included in the scope of support.
Q13. Does it also handle Google Docs, Sheets, and Slides files?
No. Google format files created directly in Google Drive are not the target. Uploaded files such as Office documents, PDFs, and Hangul documents are the target.